8 Over The Air Provisioning (OTAP) > 8.5 Java File Format

8.5
In general, all Java files have to comply with the IMP-NG and ME specifications. There are cer­tain components of the JAD file that the developer must pay attention to when using OTAP:
•
MIDlet-Jar-URL: make sure that this parameter points to a location on the network where your latest JAR files will be located, e.g. http://192.168.1.3/datafiles/mytest.jar, not in the filesystem like file://a:/java/mytest/mytest.jar. Otherwise this JAD file is useless for OTAP.
•
MIDlet-Install-Notify: this is an optional entry specifying a URL to which the result of an update/install operation is posted. That is the only way to get any feedback about the out­come of an install/update operation. The format of the posted URL complies with the IMP-NG OTA Provisioning specification. In contrast to the jar and jad file this URL must not be protected by basic authentication.
•
MIDlet-Delete-Notify: this is an optional entry specifying a URL to which the result of a delete operation is posted. That is the only way to get any feedback about the outcome of a delete operation. The format of the posted URL complies with the IMP-NG OTA Provision­ing specification. In contrast to the jar and jad file this URL must not be protected by basic authentication.
•
MIDlet-Name, MIDlet-Version, MIDlet-Vendor: are mandatory entries in the JAD and Man­ifest file. Both files must contain equal values, otherwise result 905 (see Section 8.7) is returned.
•
Example:
A suitable Manifest file for the JAD file above might look like: